Natality support #93
Merged
Natality support #93
+7,033
−74
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
smacadam
force-pushed
the
natality-support
branch
from
93ea7ec to
9db0064
Compare
RobertScalfani
approved these changes
Sep 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds support for parsing BFDR messages. A flag was added to the app settings file so the BFDR messaging can be turned on and off. This will allow us to have one baseline so we can continue using Test to test the library updates and deploy to prod with just flipping the BFDREnabled flag from true to false in the configuration.
This also uses the new message header validation function that was added to the vrdr-dotnet library.